Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 097de7d2608bb18b2d981ba7d286e230b20ac4cd2fd5fff435734b5ef880f8e6

Tx prefix hash: 4df1a3fe8fcb699e29b96e002401e7a43ecaef90121af7d2a6f3ffaed2533e07
Tx public key: 33a529445149ce5c165e161dad7fa9acc6d8a8866ac9dc1b40b12e1c290b0fbb
Timestamp: 1706651915 Timestamp [UCT]: 2024-01-30 21:58:35 Age [y:d:h:m:s]: 01:283:23:49:13
Block: 946875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461767 RingCT/type: yes/0
Extra: 0133a529445149ce5c165e161dad7fa9acc6d8a8866ac9dc1b40b12e1c290b0fbb0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef28aa33d373485495ab6cc7001eb853d626e61420f48d59f94aa23950084c73 0.600000000000 1405217 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": 946885, "vin": [ { "gen": { "height": 946875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef28aa33d373485495ab6cc7001eb853d626e61420f48d59f94aa23950084c73" } } ], "extra": [ 1, 51, 165, 41, 68, 81, 73, 206, 92, 22, 94, 22, 29, 173, 127, 169, 172, 198, 216, 168, 134, 106, 201, 220, 27, 64, 177, 46, 28, 41, 11, 15, 187, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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