Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e9ccb5d8f41cdeef707ef0b3a33aa1b564605b1e18dc8784fbddd25b85fd024

Tx prefix hash: 5a2b3132a7116bfb83e97519b2ec2caeb650a9d2c31c8e2bcaef9b8241eccd3f
Tx public key: 5c2e75ec85a9f85a4dce78a7aa841e02c78d90f60e4ca7be224f35bf4a166b49
Timestamp: 1724258088 Timestamp [UCT]: 2024-08-21 16:34:48 Age [y:d:h:m:s]: 00:249:06:19:02
Block: 1092870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178022 RingCT/type: yes/0
Extra: 015c2e75ec85a9f85a4dce78a7aa841e02c78d90f60e4ca7be224f35bf4a166b49021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fea3aa2877f9a0e5c415177ca3f053ebf2740803291cc64f69d69752a6e094eb 0.600000000000 1567701 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": 1092880, "vin": [ { "gen": { "height": 1092870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fea3aa2877f9a0e5c415177ca3f053ebf2740803291cc64f69d69752a6e094eb" } } ], "extra": [ 1, 92, 46, 117, 236, 133, 169, 248, 90, 77, 206, 120, 167, 170, 132, 30, 2, 199, 141, 144, 246, 14, 76, 167, 190, 34, 79, 53, 191, 74, 22, 107, 73, 2, 17, 0, 0, 0, 5, 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