Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779ccd78f0e5cfcab702b0451bc353f072f8bf73b9bb24d79d860e60dc8e3614

Tx prefix hash: c4749cc7a53626e8dcf5c6a67d0f353d16e573aaabd61c1c5e6acd0cafa70a43
Tx public key: 3033e5345951465a8adec357621a5a0d2dd464cd32f566a4932b3523af84025a
Timestamp: 1700452042 Timestamp [UCT]: 2023-11-20 03:47:22 Age [y:d:h:m:s]: 01:126:05:47:22
Block: 895491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351392 RingCT/type: yes/0
Extra: 013033e5345951465a8adec357621a5a0d2dd464cd32f566a4932b3523af84025a02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.662013081000 dcy

stealth address amount amount idx
00: b6c7db71d2748da6af66d36f846acd6f607779fdb81a094c07c5adbd48e74b4a 0.662013081000 1351728 of 0

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": 895501, "vin": [ { "gen": { "height": 895491 } } ], "vout": [ { "amount": 662013081, "target": { "key": "b6c7db71d2748da6af66d36f846acd6f607779fdb81a094c07c5adbd48e74b4a" } } ], "extra": [ 1, 48, 51, 229, 52, 89, 81, 70, 90, 138, 222, 195, 87, 98, 26, 90, 13, 45, 212, 100, 205, 50, 245, 102, 164, 147, 43, 53, 35, 175, 132, 2, 90, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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