Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44c182357b742b6b050b758570b92827adbf593b11d8dc536cbba31498cd2f30

Tx prefix hash: b39d03290e2b40dc9d99d1db2de130fe5c6277dd3cf95cdf95388dcab8283e4c
Tx public key: a4d462d4e9a3c763749d5bea98857d8cc932faea02504f81b82dbd658029d47e
Timestamp: 1734124082 Timestamp [UCT]: 2024-12-13 21:08:02 Age [y:d:h:m:s]: 00:187:15:07:56
Block: 1174551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133784 RingCT/type: yes/0
Extra: 01a4d462d4e9a3c763749d5bea98857d8cc932faea02504f81b82dbd658029d47e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f77832ae49266516a4f7b472cbd2b1125971ee409ed019df642f42f6a282fba5 0.600000000000 1660716 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": 1174561, "vin": [ { "gen": { "height": 1174551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f77832ae49266516a4f7b472cbd2b1125971ee409ed019df642f42f6a282fba5" } } ], "extra": [ 1, 164, 212, 98, 212, 233, 163, 199, 99, 116, 157, 91, 234, 152, 133, 125, 140, 201, 50, 250, 234, 2, 80, 79, 129, 184, 45, 189, 101, 128, 41, 212, 126, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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