Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 390be5c95d377b6245a2833646a996525b7f6839aaa1e919db4330867e90ddbe

Tx prefix hash: 85f2a591d23ff426005e82048c52c23d3d97cb96299b953fb9256364807cc783
Tx public key: ce10d5f0ee23567f0a7122bbe31dfd7ff4919b5e9ece8d4b5e4221d25fa7b095
Timestamp: 1702879043 Timestamp [UCT]: 2023-12-18 05:57:23 Age [y:d:h:m:s]: 01:117:20:51:06
Block: 915615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345391 RingCT/type: yes/0
Extra: 01ce10d5f0ee23567f0a7122bbe31dfd7ff4919b5e9ece8d4b5e4221d25fa7b09502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d068c7e269646b1e12f94a0dc94310efe93dbc37bc963a1317bdf0692faf739 0.600000000000 1373011 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": 915625, "vin": [ { "gen": { "height": 915615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d068c7e269646b1e12f94a0dc94310efe93dbc37bc963a1317bdf0692faf739" } } ], "extra": [ 1, 206, 16, 213, 240, 238, 35, 86, 127, 10, 113, 34, 187, 227, 29, 253, 127, 244, 145, 155, 94, 158, 206, 141, 75, 94, 66, 33, 210, 95, 167, 176, 149, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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