Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 848ecc86798d5ab202eb1413868030349f4d1f82e7f9e0e84e74f79e5e217f30

Tx prefix hash: 25991edb7bba2d0ecd71849adfe73dbcfc7d162781debbe2df114c4ee43ad5e4
Tx public key: 49f7db998f8355f3ecb65c379601b1a23944295ac65ff46a3a6f489e9e46fc2f
Timestamp: 1707609200 Timestamp [UCT]: 2024-02-10 23:53:20 Age [y:d:h:m:s]: 01:091:16:06:53
Block: 954823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326582 RingCT/type: yes/0
Extra: 0149f7db998f8355f3ecb65c379601b1a23944295ac65ff46a3a6f489e9e46fc2f02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4481fb5a7abb5e73213c64fe1c10bfd485b506754b067b7a8ab8855f28d2e30 0.600000000000 1414105 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": 954833, "vin": [ { "gen": { "height": 954823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4481fb5a7abb5e73213c64fe1c10bfd485b506754b067b7a8ab8855f28d2e30" } } ], "extra": [ 1, 73, 247, 219, 153, 143, 131, 85, 243, 236, 182, 92, 55, 150, 1, 177, 162, 57, 68, 41, 90, 198, 95, 244, 106, 58, 111, 72, 158, 158, 70, 252, 47, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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