Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44dfde0c3991ba7645d7e08ef4402e7e71b288b4173439be0f07e5fc5040d926

Tx prefix hash: 54478ea7e6c8a46a8f4274cfac4930b36dbabd97115ec8a92a6008bb67861905
Tx public key: 1dbb3187b3f193188e2c352d6b5e0ffbf67975638889ec3664b1a93aa37c1e2a
Timestamp: 1702023621 Timestamp [UCT]: 2023-12-08 08:20:21 Age [y:d:h:m:s]: 01:054:10:37:33
Block: 908526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300024 RingCT/type: yes/0
Extra: 011dbb3187b3f193188e2c352d6b5e0ffbf67975638889ec3664b1a93aa37c1e2a02110000000cfaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7787c8ef404adbb1e6ed2f0ed13a358721e2b6e0f35448f17995d268824a61b0 0.600000000000 1365559 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": 908536, "vin": [ { "gen": { "height": 908526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7787c8ef404adbb1e6ed2f0ed13a358721e2b6e0f35448f17995d268824a61b0" } } ], "extra": [ 1, 29, 187, 49, 135, 179, 241, 147, 24, 142, 44, 53, 45, 107, 94, 15, 251, 246, 121, 117, 99, 136, 137, 236, 54, 100, 177, 169, 58, 163, 124, 30, 42, 2, 17, 0, 0, 0, 12, 250, 243, 92, 156, 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