Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61d314f25959ad4cc0b326787ea09733628e9e62f0e02298132a66ddb2b16793

Tx prefix hash: d329b6bae2adf2e281ecd660ff32337bbccf05f8d9c7b36868d33b6bab69c847
Tx public key: 38fd778f20c23289a4bde989fbf8fb0afe0d968afd77750b27c28ab1340f4119
Timestamp: 1723691423 Timestamp [UCT]: 2024-08-15 03:10:23 Age [y:d:h:m:s]: 00:238:19:55:41
Block: 1088158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170572 RingCT/type: yes/0
Extra: 0138fd778f20c23289a4bde989fbf8fb0afe0d968afd77750b27c28ab1340f4119021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfe5ebcc4a8921e4ad8f038020e6c884902536f88e441e9de77db8fe83c7e6e8 0.600000000000 1562771 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": 1088168, "vin": [ { "gen": { "height": 1088158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfe5ebcc4a8921e4ad8f038020e6c884902536f88e441e9de77db8fe83c7e6e8" } } ], "extra": [ 1, 56, 253, 119, 143, 32, 194, 50, 137, 164, 189, 233, 137, 251, 248, 251, 10, 254, 13, 150, 138, 253, 119, 117, 11, 39, 194, 138, 177, 52, 15, 65, 25, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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