Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 570eafb307b63f70a29abcf61f3ef194124d4bdd15bf6b66226e0a34757b70d3

Tx prefix hash: a0c61f474520ee1f142c64716a24f8d492d14747c0eea0f022264c7aae7cf0f2
Tx public key: 64f1bc48ef5604d7077f158e5f6046a58dbb5b21f880185cb27bcb74062f3ead
Timestamp: 1716986561 Timestamp [UCT]: 2024-05-29 12:42:41 Age [y:d:h:m:s]: 00:306:12:12:00
Block: 1032575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219055 RingCT/type: yes/0
Extra: 0164f1bc48ef5604d7077f158e5f6046a58dbb5b21f880185cb27bcb74062f3ead02110000000379bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aee6be00fd6648af109e25825cac1e081b031a1f885f90e8d27c95ca0c0b3a82 0.600000000000 1501028 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": 1032585, "vin": [ { "gen": { "height": 1032575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aee6be00fd6648af109e25825cac1e081b031a1f885f90e8d27c95ca0c0b3a82" } } ], "extra": [ 1, 100, 241, 188, 72, 239, 86, 4, 215, 7, 127, 21, 142, 95, 96, 70, 165, 141, 187, 91, 33, 248, 128, 24, 92, 178, 123, 203, 116, 6, 47, 62, 173, 2, 17, 0, 0, 0, 3, 121, 189, 163, 190, 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