Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51c6c8c7e275c097f74c9c0cf16e1db94a95ccdda746cfbe721e921d29a9f4c5

Tx prefix hash: f24e7997cfcb14c9a248c1c2780ef4dfa1190ca9d8a09d349d577802c6e4b2b4
Tx public key: 8a7bddb2e9c181326d9778ffab99f9166541eb6ebe104595b013bc0e7812fe77
Timestamp: 1650133501 Timestamp [UCT]: 2022-04-16 18:25:01 Age [y:d:h:m:s]: 02:290:11:52:12
Block: 481572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 727321 RingCT/type: yes/0
Extra: 018a7bddb2e9c181326d9778ffab99f9166541eb6ebe104595b013bc0e7812fe77021100000004bf7ee4e7000000000000000000

1 output(s) for total of 15.572282956000 dcy

stealth address amount amount idx
00: 9eff6c6fd7c79ef4b770b1b546ab86ae53c47e5e4ddbc33cfbb57e1e00b7b4e3 15.572282956000 902875 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": 481582, "vin": [ { "gen": { "height": 481572 } } ], "vout": [ { "amount": 15572282956, "target": { "key": "9eff6c6fd7c79ef4b770b1b546ab86ae53c47e5e4ddbc33cfbb57e1e00b7b4e3" } } ], "extra": [ 1, 138, 123, 221, 178, 233, 193, 129, 50, 109, 151, 120, 255, 171, 153, 249, 22, 101, 65, 235, 110, 190, 16, 69, 149, 176, 19, 188, 14, 120, 18, 254, 119, 2, 17, 0, 0, 0, 4, 191, 126, 228, 231, 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