Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7cde77cb8c4573a8a254191a04fd50a05dda0cad80e63dc947479cf27f7ee3f

Tx prefix hash: b42ced7033e01e3842db5557d2cf8630ea3df38b159c9edce637840e6b7f33f4
Tx public key: 827bfc3b657aae8ce5d6768f3954dfb5bce41f987b652a5828802883c8ee1b23
Timestamp: 1732434061 Timestamp [UCT]: 2024-11-24 07:41:01 Age [y:d:h:m:s]: 00:132:02:57:24
Block: 1160545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94239 RingCT/type: yes/0
Extra: 01827bfc3b657aae8ce5d6768f3954dfb5bce41f987b652a5828802883c8ee1b23021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a1e0d83b647568156ae05748cd95017f692cad0177ffd05a2c7037ecdd58c42 0.600000000000 1646192 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": 1160555, "vin": [ { "gen": { "height": 1160545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a1e0d83b647568156ae05748cd95017f692cad0177ffd05a2c7037ecdd58c42" } } ], "extra": [ 1, 130, 123, 252, 59, 101, 122, 174, 140, 229, 214, 118, 143, 57, 84, 223, 181, 188, 228, 31, 152, 123, 101, 42, 88, 40, 128, 40, 131, 200, 238, 27, 35, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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