Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4eb2e32fa8d8eb6eb8ffd9260c1c26c8f33be90e7e1ac1d0247d4174020eb3bc

Tx prefix hash: 3f110f973f81c67a0a0aaa637d123bcbf60be9a79b2f5d8eef614e99e0b16234
Tx public key: 58b725c8fe076b2b8cc868628aeb99ad95130d0cf62877a789f97ce4bbca02b6
Timestamp: 1723556705 Timestamp [UCT]: 2024-08-13 13:45:05 Age [y:d:h:m:s]: 01:162:10:19:20
Block: 1087045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374515 RingCT/type: yes/0
Extra: 0158b725c8fe076b2b8cc868628aeb99ad95130d0cf62877a789f97ce4bbca02b602110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 607d918b3b4f5fe75b37f48703ef6da9a63690a37af9173183edab1e18a07c3f 0.600000000000 1561648 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": 1087055, "vin": [ { "gen": { "height": 1087045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "607d918b3b4f5fe75b37f48703ef6da9a63690a37af9173183edab1e18a07c3f" } } ], "extra": [ 1, 88, 183, 37, 200, 254, 7, 107, 43, 140, 200, 104, 98, 138, 235, 153, 173, 149, 19, 13, 12, 246, 40, 119, 167, 137, 249, 124, 228, 187, 202, 2, 182, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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