Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 798375559c3549797b4e3c1ed4af8367859d76891636b61a01bcefd0ccbf1c07

Tx prefix hash: 337a51958721bd35f53c51541324e8b25f7d88752ae79c9c618037b7c90b3bf9
Tx public key: ed12774d14f4671f3633b01c4c1e23dd4189b04d5c3a69da9c3fbb9462d4500f
Timestamp: 1704560153 Timestamp [UCT]: 2024-01-06 16:55:53 Age [y:d:h:m:s]: 01:308:11:16:20
Block: 929536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479300 RingCT/type: yes/0
Extra: 01ed12774d14f4671f3633b01c4c1e23dd4189b04d5c3a69da9c3fbb9462d4500f02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a7e5734ebf9f2d6a269ddb544a2c37660fc92cdca97c4d7614a09145c25bb05 0.600000000000 1387412 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": 929546, "vin": [ { "gen": { "height": 929536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a7e5734ebf9f2d6a269ddb544a2c37660fc92cdca97c4d7614a09145c25bb05" } } ], "extra": [ 1, 237, 18, 119, 77, 20, 244, 103, 31, 54, 51, 176, 28, 76, 30, 35, 221, 65, 137, 176, 77, 92, 58, 105, 218, 156, 63, 187, 148, 98, 212, 80, 15, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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