Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f02dc5382bdc4f48394fcef373e7a861cece0d82ce2625cc5a2237a0c262b5

Tx prefix hash: b4a923351382481f5cf7eb6b22553f44c395ca8d0eba53143d05357f8ab25089
Tx public key: a7e1bba6d5075e95186b3b2d4dffc74a6a941d476f3ca02d0acd78a6be56c7dd
Timestamp: 1697216276 Timestamp [UCT]: 2023-10-13 16:57:56 Age [y:d:h:m:s]: 01:180:15:38:38
Block: 868870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390149 RingCT/type: yes/0
Extra: 01a7e1bba6d5075e95186b3b2d4dffc74a6a941d476f3ca02d0acd78a6be56c7dd02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.811097446000 dcy

stealth address amount amount idx
00: 02abb23abd2302913095b3c499d450bcfb7ec1c3992f7d5a42849de7791983cb 0.811097446000 1323691 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": 868880, "vin": [ { "gen": { "height": 868870 } } ], "vout": [ { "amount": 811097446, "target": { "key": "02abb23abd2302913095b3c499d450bcfb7ec1c3992f7d5a42849de7791983cb" } } ], "extra": [ 1, 167, 225, 187, 166, 213, 7, 94, 149, 24, 107, 59, 45, 77, 255, 199, 74, 106, 148, 29, 71, 111, 60, 160, 45, 10, 205, 120, 166, 190, 86, 199, 221, 2, 17, 0, 0, 0, 4, 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