Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2b4ed413bcae77b739a4d0e0922f72d26fe6e6d6ebb1cfff27349bb677411416

Tx prefix hash: 30182a46a4b61aa35cf54898df5b8cbe4f099d9c175e1cf732f159a2f560491a
Tx public key: 79212f435148dfaee1c3457d86652f867dfbe7e5c5d6eff8d22178d7513117e5
Timestamp: 1695756235 Timestamp [UCT]: 2023-09-26 19:23:55 Age [y:d:h:m:s]: 01:192:16:48:59
Block: 856755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398785 RingCT/type: yes/0
Extra: 0179212f435148dfaee1c3457d86652f867dfbe7e5c5d6eff8d22178d7513117e502110000000533af99f4000000000000000000

1 output(s) for total of 0.889641586000 dcy

stealth address amount amount idx
00: da3630f8c9aed84ae525d0fd85613f012b51bd142f177c8d0bc5799bab2f3ed7 0.889641586000 1310843 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 856765, "vin": [ { "gen": { "height": 856755 } } ], "vout": [ { "amount": 889641586, "target": { "key": "da3630f8c9aed84ae525d0fd85613f012b51bd142f177c8d0bc5799bab2f3ed7" } } ], "extra": [ 1, 121, 33, 47, 67, 81, 72, 223, 174, 225, 195, 69, 125, 134, 101, 47, 134, 125, 251, 231, 229, 197, 214, 239, 248, 210, 33, 120, 215, 81, 49, 23, 229, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8