Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c70cc8fb3b4c0132e626192cc3af275e0452e0d0507a22e94e531c7bd450e06

Tx prefix hash: adb729917ba08f4620a40c3e5b91f54f33980748dddbfce485ddfce39393f642
Tx public key: 863d96c75525177f413efa461fa4e6f29cd14d0fb6d5889ba5a58e6b9a028fe8
Timestamp: 1722591653 Timestamp [UCT]: 2024-08-02 09:40:53 Age [y:d:h:m:s]: 00:160:02:08:20
Block: 1079039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114537 RingCT/type: yes/0
Extra: 01863d96c75525177f413efa461fa4e6f29cd14d0fb6d5889ba5a58e6b9a028fe802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd2e95d29e1cee7fe4a2c56caccc94512e408918245e745a498a843775533333 0.600000000000 1551824 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": 1079049, "vin": [ { "gen": { "height": 1079039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd2e95d29e1cee7fe4a2c56caccc94512e408918245e745a498a843775533333" } } ], "extra": [ 1, 134, 61, 150, 199, 85, 37, 23, 127, 65, 62, 250, 70, 31, 164, 230, 242, 156, 209, 77, 15, 182, 213, 136, 155, 165, 165, 142, 107, 154, 2, 143, 232, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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