Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b46abc21b2da30f3ff173753f58ffac59be5485a1e8bc4c53c4fd236a17a47a

Tx prefix hash: c89c55b77017e5bb8e9537235a8a0c6bb5a6fe144aea974f105d89bd6ecebbdf
Tx public key: 7acd65ba7da2996351f3292ad4f480b91b04b3c487d1f12279f7e0da5bd9ef2e
Timestamp: 1705347159 Timestamp [UCT]: 2024-01-15 19:32:39 Age [y:d:h:m:s]: 01:295:23:11:09
Block: 936058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470332 RingCT/type: yes/0
Extra: 017acd65ba7da2996351f3292ad4f480b91b04b3c487d1f12279f7e0da5bd9ef2e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea2cac8d0b5d75fa3c0d4fe32376ceea7bb6d0302f3a2e8e994d2464740a59ae 0.600000000000 1394080 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": 936068, "vin": [ { "gen": { "height": 936058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea2cac8d0b5d75fa3c0d4fe32376ceea7bb6d0302f3a2e8e994d2464740a59ae" } } ], "extra": [ 1, 122, 205, 101, 186, 125, 162, 153, 99, 81, 243, 41, 42, 212, 244, 128, 185, 27, 4, 179, 196, 135, 209, 241, 34, 121, 247, 224, 218, 91, 217, 239, 46, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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