Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dcb4d6ce5e65deead4741132538ad4393f3c54eff81c370891cc4e2d94df02d

Tx prefix hash: b3640697a6914dbcc17a0cdfbbd448fd90c03ca8f917cfa0a431ce4d92156844
Tx public key: 0733200d6489e92a6f36ee5d1974d5144dbd5a99053b472865a74dbad1d2f1ef
Timestamp: 1716864369 Timestamp [UCT]: 2024-05-28 02:46:09 Age [y:d:h:m:s]: 01:001:04:10:11
Block: 1031573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261751 RingCT/type: yes/0
Extra: 010733200d6489e92a6f36ee5d1974d5144dbd5a99053b472865a74dbad1d2f1ef0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 702e5b332c476dfb06e3bcb02dc45d19bb2b290e5c6b965c2346fd70315d8f8c 0.600000000000 1500022 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": 1031583, "vin": [ { "gen": { "height": 1031573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "702e5b332c476dfb06e3bcb02dc45d19bb2b290e5c6b965c2346fd70315d8f8c" } } ], "extra": [ 1, 7, 51, 32, 13, 100, 137, 233, 42, 111, 54, 238, 93, 25, 116, 213, 20, 77, 189, 90, 153, 5, 59, 71, 40, 101, 167, 77, 186, 209, 210, 241, 239, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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