Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b85086f10166f5b0629c805884872ef27449956d9aa6e80136e7168a78c95ba7

Tx prefix hash: 92c5502482d8101f78d07e56bb76849b8b32bafbfa5a82cd60a7ed49d26fca3b
Tx public key: 2bbd654ddec4669c6be3d4fa0ba78f4f2fac10af8b94053f5ceea314d0cc71e3
Timestamp: 1713382820 Timestamp [UCT]: 2024-04-17 19:40:20 Age [y:d:h:m:s]: 00:314:04:48:57
Block: 1002691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224597 RingCT/type: yes/0
Extra: 012bbd654ddec4669c6be3d4fa0ba78f4f2fac10af8b94053f5ceea314d0cc71e302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b84790359cf62646f3669d846eaacafcb1ada907d7ca65e1ae25dced15b95ce 0.600000000000 1463211 of 15

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": 1002701, "vin": [ { "gen": { "height": 1002691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b84790359cf62646f3669d846eaacafcb1ada907d7ca65e1ae25dced15b95ce" } } ], "extra": [ 1, 43, 189, 101, 77, 222, 196, 102, 156, 107, 227, 212, 250, 11, 167, 143, 79, 47, 172, 16, 175, 139, 148, 5, 63, 92, 238, 163, 20, 208, 204, 113, 227, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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