Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6efffcf38aecd2a85928eb99e16e2f1ac88fcad6c8f86f9747fc5dffcf71e876

Tx prefix hash: b3d6ad52d374afdedff280ad308d47d6f8b53f802ed3e2efa3843dc988b45e2d
Tx public key: b1419994488f8b689d9ba44e7652f21a89b1da30c9c45800dd7b743546783d25
Timestamp: 1711551937 Timestamp [UCT]: 2024-03-27 15:05:37 Age [y:d:h:m:s]: 01:236:21:46:47
Block: 987543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427985 RingCT/type: yes/0
Extra: 01b1419994488f8b689d9ba44e7652f21a89b1da30c9c45800dd7b743546783d2502110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a91d27a3a8cfc7a7c13e7d221ca49ea3b2823727e31421ae2214b38e284eb9b 0.600000000000 1447794 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": 987553, "vin": [ { "gen": { "height": 987543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a91d27a3a8cfc7a7c13e7d221ca49ea3b2823727e31421ae2214b38e284eb9b" } } ], "extra": [ 1, 177, 65, 153, 148, 72, 143, 139, 104, 157, 155, 164, 78, 118, 82, 242, 26, 137, 177, 218, 48, 201, 196, 88, 0, 221, 123, 116, 53, 70, 120, 61, 37, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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