Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3556d632b6d72ab726ca32728c2f7c1c0ad12ff3233aaa6c88f63f8e32919447

Tx prefix hash: ec35177d320a7e4be039a64ec74b7f74c627431c18853b08716392720631ee81
Tx public key: 1c54f946f8ffa089546c8eb44cbc7b193d3563ac9e5a90e13f5c360cbc88fd87
Timestamp: 1709275852 Timestamp [UCT]: 2024-03-01 06:50:52 Age [y:d:h:m:s]: 01:103:00:46:15
Block: 968662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334637 RingCT/type: yes/0
Extra: 011c54f946f8ffa089546c8eb44cbc7b193d3563ac9e5a90e13f5c360cbc88fd870211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c79f760efe4a8c6bb1c13a6ca7e2d57e9d1c39a1874be8f77909e9589d47326 0.600000000000 1428479 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": 968672, "vin": [ { "gen": { "height": 968662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c79f760efe4a8c6bb1c13a6ca7e2d57e9d1c39a1874be8f77909e9589d47326" } } ], "extra": [ 1, 28, 84, 249, 70, 248, 255, 160, 137, 84, 108, 142, 180, 76, 188, 123, 25, 61, 53, 99, 172, 158, 90, 144, 225, 63, 92, 54, 12, 188, 136, 253, 135, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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