Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 760bf754469fabfee4a29de59caeb8460c4fdc4a6b3d59dc52487d19807245a2

Tx prefix hash: 34a5fa516c056c113006ffae7e14d16db51e4c694e11641173d4a663b9d807cb
Tx public key: e5e7b8d844a78a6129553c1b6b21e0f43b56b7298485d0dab8744ce7afcc79af
Timestamp: 1704479989 Timestamp [UCT]: 2024-01-05 18:39:49 Age [y:d:h:m:s]: 01:103:06:12:39
Block: 928876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334903 RingCT/type: yes/0
Extra: 01e5e7b8d844a78a6129553c1b6b21e0f43b56b7298485d0dab8744ce7afcc79af0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e77955d19f29552d0e372e2bffef7e6ee67b7213ddb2d2488a6807307b728830 0.600000000000 1386740 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": 928886, "vin": [ { "gen": { "height": 928876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e77955d19f29552d0e372e2bffef7e6ee67b7213ddb2d2488a6807307b728830" } } ], "extra": [ 1, 229, 231, 184, 216, 68, 167, 138, 97, 41, 85, 60, 27, 107, 33, 224, 244, 59, 86, 183, 41, 132, 133, 208, 218, 184, 116, 76, 231, 175, 204, 121, 175, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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