Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4660644c6ad45f79f02a202646a8d9d9b81b5487cd93abf93f0ae6f5f198f17b

Tx prefix hash: ee981aa5cb7175eec0e17a7949cddbb5339bdefe6f826f5869ab76926ba53afe
Tx public key: 58148241ede1d27532b341e81cadf9165263e8b0a932108da497c30d32705ea9
Timestamp: 1703131407 Timestamp [UCT]: 2023-12-21 04:03:27 Age [y:d:h:m:s]: 01:144:13:52:19
Block: 917729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364463 RingCT/type: yes/0
Extra: 0158148241ede1d27532b341e81cadf9165263e8b0a932108da497c30d32705ea902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b29e409490a150190cc587e2c95f362d598d39d4e9d25ba6d59f83f77d2b3a37 0.600000000000 1375311 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": 917739, "vin": [ { "gen": { "height": 917729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b29e409490a150190cc587e2c95f362d598d39d4e9d25ba6d59f83f77d2b3a37" } } ], "extra": [ 1, 88, 20, 130, 65, 237, 225, 210, 117, 50, 179, 65, 232, 28, 173, 249, 22, 82, 99, 232, 176, 169, 50, 16, 141, 164, 151, 195, 13, 50, 112, 94, 169, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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