Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dccbd885b764650e94bc9b89a4c50185103f66b75dd23a38a4ed1a03286134f

Tx prefix hash: 38e0d66d32092bf42db48576fc0ce2ab33f95406ae847b50cf03ba6e6218f4c6
Tx public key: 912335fc192c08d93e8aaee54fdb2a4e69e5f209ca2d6036e1d8b6ddb4a5e7a4
Timestamp: 1707198156 Timestamp [UCT]: 2024-02-06 05:42:36 Age [y:d:h:m:s]: 00:282:20:18:26
Block: 951411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202512 RingCT/type: yes/0
Extra: 01912335fc192c08d93e8aaee54fdb2a4e69e5f209ca2d6036e1d8b6ddb4a5e7a402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a42d6d33dd9c9a0f1a9310a77d439448053d5e4a4b1eb5fbd7898dbffe73ae7f 0.600000000000 1410173 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": 951421, "vin": [ { "gen": { "height": 951411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a42d6d33dd9c9a0f1a9310a77d439448053d5e4a4b1eb5fbd7898dbffe73ae7f" } } ], "extra": [ 1, 145, 35, 53, 252, 25, 44, 8, 217, 62, 138, 174, 229, 79, 219, 42, 78, 105, 229, 242, 9, 202, 45, 96, 54, 225, 216, 182, 221, 180, 165, 231, 164, 2, 17, 0, 0, 0, 3, 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