Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fb6728e49f92478238ed5ff1dc8185e10ccd75a1235c59829308b383721f29d

Tx prefix hash: 381ec396963f83d1f703593ed161ea9116dab93e327c8877d12ae3c8ac48a2c4
Tx public key: 37d92ce9d042cdd1c73844844a7acc3514fbccf7bb76f537c7f104f62d74f978
Timestamp: 1669452609 Timestamp [UCT]: 2022-11-26 08:50:09 Age [y:d:h:m:s]: 02:160:21:54:51
Block: 639387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636743 RingCT/type: yes/0
Extra: 0137d92ce9d042cdd1c73844844a7acc3514fbccf7bb76f537c7f104f62d74f97802110000000575e3f0e9000000000000000000

1 output(s) for total of 4.671382709000 dcy

stealth address amount amount idx
00: ebee35e53be12bfba9b2e8fe2b119bdf005e49a95a3fe66decfe66b1c7f96088 4.671382709000 1079036 of 0

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": 639397, "vin": [ { "gen": { "height": 639387 } } ], "vout": [ { "amount": 4671382709, "target": { "key": "ebee35e53be12bfba9b2e8fe2b119bdf005e49a95a3fe66decfe66b1c7f96088" } } ], "extra": [ 1, 55, 217, 44, 233, 208, 66, 205, 209, 199, 56, 68, 132, 74, 122, 204, 53, 20, 251, 204, 247, 187, 118, 245, 55, 199, 241, 4, 246, 45, 116, 249, 120, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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