Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fbfad2c786a1e606186eb44de4c12d6b4ec51ea3a39a3d3f324a3092873f211

Tx prefix hash: be36a57c6ceae18da6b5f8bcabd1a320e8a4994fa582d68c9302168ece0b2014
Tx public key: 8b1148a410cf7b0e6a178f5d364445de8c5ef8d2d2f5b213e18fd2cb55470e36
Timestamp: 1731845129 Timestamp [UCT]: 2024-11-17 12:05:29 Age [y:d:h:m:s]: 01:004:01:45:01
Block: 1155663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261323 RingCT/type: yes/0
Extra: 018b1148a410cf7b0e6a178f5d364445de8c5ef8d2d2f5b213e18fd2cb55470e360211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dd6edd0522555a47859124af0db13e416acd3f89e27092839a1d29fc5ce89df 0.600000000000 1641280 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": 1155673, "vin": [ { "gen": { "height": 1155663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dd6edd0522555a47859124af0db13e416acd3f89e27092839a1d29fc5ce89df" } } ], "extra": [ 1, 139, 17, 72, 164, 16, 207, 123, 14, 106, 23, 143, 93, 54, 68, 69, 222, 140, 94, 248, 210, 210, 245, 178, 19, 225, 143, 210, 203, 85, 71, 14, 54, 2, 17, 0, 0, 0, 2, 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