Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27210857e27fe35192c4984c021abade33afc9f676c6a5344be3da248a533916

Tx prefix hash: 0bd5d1986b6c9f32e3c65b3248c8b57f30fca1156291d6e21887938c22a58825
Tx public key: b3c7313cbe52cde9791d41dc004aa85c767a31e8445125fb3b7b5506f8cefde1
Timestamp: 1701016785 Timestamp [UCT]: 2023-11-26 16:39:45 Age [y:d:h:m:s]: 01:355:12:38:38
Block: 900175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512983 RingCT/type: yes/0
Extra: 01b3c7313cbe52cde9791d41dc004aa85c767a31e8445125fb3b7b5506f8cefde1021100000005faf35c9c000000000000000000

1 output(s) for total of 0.638772966000 dcy

stealth address amount amount idx
00: 40d6515ae6f7136a06c6b58132a01bb001468872d5820fdf1c0560acb6f50e55 0.638772966000 1356652 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": 900185, "vin": [ { "gen": { "height": 900175 } } ], "vout": [ { "amount": 638772966, "target": { "key": "40d6515ae6f7136a06c6b58132a01bb001468872d5820fdf1c0560acb6f50e55" } } ], "extra": [ 1, 179, 199, 49, 60, 190, 82, 205, 233, 121, 29, 65, 220, 0, 74, 168, 92, 118, 122, 49, 232, 68, 81, 37, 251, 59, 123, 85, 6, 248, 206, 253, 225, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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