Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3ff2c7deaa7c11bd29cbc79ad05c33501a5c6c22952d4d3f365bec8c2ed35b8

Tx prefix hash: 6a948a85279cf44f4de6c26084af0247d595cfe956cb69f8cb1fe727862381a6
Tx public key: 7827587d670d7696b87179c54ca770444c979ef4a327a3357deda35a8b72d802
Timestamp: 1648429862 Timestamp [UCT]: 2022-03-28 01:11:02 Age [y:d:h:m:s]: 03:195:19:58:16
Block: 467879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 917821 RingCT/type: yes/0
Extra: 017827587d670d7696b87179c54ca770444c979ef4a327a3357deda35a8b72d802021100000016a8c141c5000000000000000000

1 output(s) for total of 17.287130073000 dcy

stealth address amount amount idx
00: 346ff5b485a488f0f2bbd830da2278b233e7ed5c06e44d9d09f9df401c703924 17.287130073000 886479 of 0

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": 467889, "vin": [ { "gen": { "height": 467879 } } ], "vout": [ { "amount": 17287130073, "target": { "key": "346ff5b485a488f0f2bbd830da2278b233e7ed5c06e44d9d09f9df401c703924" } } ], "extra": [ 1, 120, 39, 88, 125, 103, 13, 118, 150, 184, 113, 121, 197, 76, 167, 112, 68, 76, 151, 158, 244, 163, 39, 163, 53, 125, 237, 163, 90, 139, 114, 216, 2, 2, 17, 0, 0, 0, 22, 168, 193, 65, 197, 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