Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d85bca49a0bff4884c38818f080c2efac7e19096f9a096432172550436e0c9b

Tx prefix hash: f1ae11d7e9d4abb442d4991f35b957fc7291a6fbb49fe209c8f78bb2cb0e38ea
Tx public key: aa580a120731df198b482d506f1f7da2217a9e7a226d085ad8ef6b7618c370a5
Timestamp: 1644684213 Timestamp [UCT]: 2022-02-12 16:43:33 Age [y:d:h:m:s]: 02:109:20:45:58
Block: 437133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597617 RingCT/type: yes/0
Extra: 01aa580a120731df198b482d506f1f7da2217a9e7a226d085ad8ef6b7618c370a50211000000014a0f5013000000000000000000

1 output(s) for total of 21.859634873000 dcy

stealth address amount amount idx
00: 11ab238629bf97dab3e2ef35791f3317ba217e1082980cb214b6d0ece51025e2 21.859634873000 848678 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": 437143, "vin": [ { "gen": { "height": 437133 } } ], "vout": [ { "amount": 21859634873, "target": { "key": "11ab238629bf97dab3e2ef35791f3317ba217e1082980cb214b6d0ece51025e2" } } ], "extra": [ 1, 170, 88, 10, 18, 7, 49, 223, 25, 139, 72, 45, 80, 111, 31, 125, 162, 33, 122, 158, 122, 34, 109, 8, 90, 216, 239, 107, 118, 24, 195, 112, 165, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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