Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e18f78d468ec69efdde902b0696843b67dcc4c20b67957fd77c5dccf39ecc55

Tx prefix hash: d88302f4a5b0294e5829928917713bfd5da2ccfeee9ca751405326b39ed01d54
Tx public key: b12ff55927160ced7c0b7fb44aa91a408455bc360e89d4e5c77a852707af6200
Timestamp: 1729482701 Timestamp [UCT]: 2024-10-21 03:51:41 Age [y:d:h:m:s]: 00:144:08:36:30
Block: 1136145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102984 RingCT/type: yes/0
Extra: 01b12ff55927160ced7c0b7fb44aa91a408455bc360e89d4e5c77a852707af6200021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cab64c598844a2318fb5da3dd6d06d1c90a5c9e6c5bf80aa1f57fd2eed4b9d15 0.600000000000 1619488 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": 1136155, "vin": [ { "gen": { "height": 1136145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cab64c598844a2318fb5da3dd6d06d1c90a5c9e6c5bf80aa1f57fd2eed4b9d15" } } ], "extra": [ 1, 177, 47, 245, 89, 39, 22, 12, 237, 124, 11, 127, 180, 74, 169, 26, 64, 132, 85, 188, 54, 14, 137, 212, 229, 199, 122, 133, 39, 7, 175, 98, 0, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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