Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f956feab20a5f589e1e0e4a70dbe7ac1da8460f73e824e4e00e2871fca796e3

Tx prefix hash: 6f9794297ffa8e9369648e4e498a85abf64418aa5320977933f735a6476d471f
Tx public key: f7a3d12c448cef1e38668559466aa73fbbb97ee08c2af238b5b829d74a2b6e57
Timestamp: 1711153963 Timestamp [UCT]: 2024-03-23 00:32:43 Age [y:d:h:m:s]: 00:361:10:58:59
Block: 984244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258430 RingCT/type: yes/0
Extra: 01f7a3d12c448cef1e38668559466aa73fbbb97ee08c2af238b5b829d74a2b6e570211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 490d91b1cf82950472cec6e4908cebe2ced61459509d3fa735c13bac0d8c20b9 0.600000000000 1444411 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": 984254, "vin": [ { "gen": { "height": 984244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "490d91b1cf82950472cec6e4908cebe2ced61459509d3fa735c13bac0d8c20b9" } } ], "extra": [ 1, 247, 163, 209, 44, 68, 140, 239, 30, 56, 102, 133, 89, 70, 106, 167, 63, 187, 185, 126, 224, 140, 42, 242, 56, 181, 184, 41, 215, 74, 43, 110, 87, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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