Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99978a35898e204b01975689a5d2dcc521c6c439aefc3353564d55148e7e2713

Tx prefix hash: 0c87f03fe45b67ec30014c8af3231c4f27780b4028e0212262c5d7a6d297f07f
Tx public key: af7c5fdb3d33c1a990a663ea60d6b51a41c1953eb2b9eaa9684cde3b8989c2ef
Timestamp: 1704376018 Timestamp [UCT]: 2024-01-04 13:46:58 Age [y:d:h:m:s]: 01:310:12:40:07
Block: 928032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480745 RingCT/type: yes/0
Extra: 01af7c5fdb3d33c1a990a663ea60d6b51a41c1953eb2b9eaa9684cde3b8989c2ef02110000000abfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d6c00e45dbb15938fb71adfde1158e342cd563fe86445b5166a2b60e8fb7676 0.600000000000 1385888 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": 928042, "vin": [ { "gen": { "height": 928032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d6c00e45dbb15938fb71adfde1158e342cd563fe86445b5166a2b60e8fb7676" } } ], "extra": [ 1, 175, 124, 95, 219, 61, 51, 193, 169, 144, 166, 99, 234, 96, 214, 181, 26, 65, 193, 149, 62, 178, 185, 234, 169, 104, 76, 222, 59, 137, 137, 194, 239, 2, 17, 0, 0, 0, 10, 191, 162, 34, 33, 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