Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc15d04bd9fce3817aa2659b4b24fc569b075d55b238c81b94d1f205a3273cea

Tx prefix hash: d663e71dd735183e92e972c86f44d95525761c886b23f6961e6bd6f0c7eb6941
Tx public key: eae734853123fe3ac93d2aa80599e6e9cce3e2c1800e5bf1f5784a9ef23f0b35
Timestamp: 1711968810 Timestamp [UCT]: 2024-04-01 10:53:30 Age [y:d:h:m:s]: 01:220:13:45:02
Block: 990938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416355 RingCT/type: yes/0
Extra: 01eae734853123fe3ac93d2aa80599e6e9cce3e2c1800e5bf1f5784a9ef23f0b3502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5221ec2d8247582827ded3c602a3ce2a5fa709853fa481b15567d3a4f8ac4070 0.600000000000 1451270 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": 990948, "vin": [ { "gen": { "height": 990938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5221ec2d8247582827ded3c602a3ce2a5fa709853fa481b15567d3a4f8ac4070" } } ], "extra": [ 1, 234, 231, 52, 133, 49, 35, 254, 58, 201, 61, 42, 168, 5, 153, 230, 233, 204, 227, 226, 193, 128, 14, 91, 241, 245, 120, 74, 158, 242, 63, 11, 53, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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