Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1459890899c25b3c471f0198f2b91f820fe713477df027410ebbe3796cadd5f3

Tx prefix hash: 3904b94a94801d7e7cd60d3e9cce6f417f3c287c1d2b81a5509072bfabea836a
Tx public key: ae4d0de4955c8d7f2f0ef840645c19a61b869e96bdbb05ac2977e83c667e6671
Timestamp: 1737715573 Timestamp [UCT]: 2025-01-24 10:46:13 Age [y:d:h:m:s]: 00:144:15:53:04
Block: 1204238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103119 RingCT/type: yes/0
Extra: 01ae4d0de4955c8d7f2f0ef840645c19a61b869e96bdbb05ac2977e83c667e667102110000001c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bece485e4e289ef3af6ed532c7afdec08a53764a1aec1d0294b9028e28ac5b5 0.600000000000 1690923 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": 1204248, "vin": [ { "gen": { "height": 1204238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bece485e4e289ef3af6ed532c7afdec08a53764a1aec1d0294b9028e28ac5b5" } } ], "extra": [ 1, 174, 77, 13, 228, 149, 92, 141, 127, 47, 14, 248, 64, 100, 92, 25, 166, 27, 134, 158, 150, 189, 187, 5, 172, 41, 119, 232, 60, 102, 126, 102, 113, 2, 17, 0, 0, 0, 28, 31, 10, 83, 235, 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