Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1baf7c82c6a898cf96cc9264320989f9d23f93c4e3394ef417956b5153a72672

Tx prefix hash: 52c2ecc259c7fc76a1cb20837f48462a0a17d59d4680f7d1cb7de02db6a716cd
Tx public key: e7a67a27f87c9eda237705ede00b8a011f1d67b02ba58edcda336e32b739b19d
Timestamp: 1731409291 Timestamp [UCT]: 2024-11-12 11:01:31 Age [y:d:h:m:s]: 00:164:09:59:53
Block: 1152049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117355 RingCT/type: yes/0
Extra: 01e7a67a27f87c9eda237705ede00b8a011f1d67b02ba58edcda336e32b739b19d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 406a1076cbea2a7e1bc426ea2ee0bd57a0a01cccf8b74f53cfd04de4262ea238 0.600000000000 1637640 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": 1152059, "vin": [ { "gen": { "height": 1152049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "406a1076cbea2a7e1bc426ea2ee0bd57a0a01cccf8b74f53cfd04de4262ea238" } } ], "extra": [ 1, 231, 166, 122, 39, 248, 124, 158, 218, 35, 119, 5, 237, 224, 11, 138, 1, 31, 29, 103, 176, 43, 165, 142, 220, 218, 51, 110, 50, 183, 57, 177, 157, 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