Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4e90d73c1442855dcc4c73005268040a0fd266eb3af91bf09cc4f1d17847930

Tx prefix hash: 46d0f9838128013c4e101bb32c8eb07b961cfbc6e6c9795315b07a3c4d506339
Tx public key: 31209db27fd2acd300b8b0d6403625c0676b4d690078790d8f7ac0ed48f0b3ac
Timestamp: 1717235290 Timestamp [UCT]: 2024-06-01 09:48:10 Age [y:d:h:m:s]: 00:298:04:57:05
Block: 1034642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213097 RingCT/type: yes/0
Extra: 0131209db27fd2acd300b8b0d6403625c0676b4d690078790d8f7ac0ed48f0b3ac021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9e1b1d19035fc8c2b0e94735637f87e99572db50e9ab24e988b572be8a438c7 0.600000000000 1503157 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": 1034652, "vin": [ { "gen": { "height": 1034642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9e1b1d19035fc8c2b0e94735637f87e99572db50e9ab24e988b572be8a438c7" } } ], "extra": [ 1, 49, 32, 157, 178, 127, 210, 172, 211, 0, 184, 176, 214, 64, 54, 37, 192, 103, 107, 77, 105, 0, 120, 121, 13, 143, 122, 192, 237, 72, 240, 179, 172, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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