Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2d384018826382980f9e5803c0676c630fe3b0e393f0c6420482eda64bc8fd8

Tx prefix hash: 182260e846fa2a5b4ae3489d7ee503a51945556d9ab3840439864a8ad18d39ba
Tx public key: d83141031e00f5f6ede648a58dbb70f62d93dceae85ec6f1a4e592d22ddb5db9
Timestamp: 1731871930 Timestamp [UCT]: 2024-11-17 19:32:10 Age [y:d:h:m:s]: 00:209:23:14:14
Block: 1155892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149827 RingCT/type: yes/0
Extra: 01d83141031e00f5f6ede648a58dbb70f62d93dceae85ec6f1a4e592d22ddb5db9021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcfbe3f777a6963832e0b8f5f8c9acd483d7a06214da4f94659c7a65b3e9f7a4 0.600000000000 1641511 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": 1155902, "vin": [ { "gen": { "height": 1155892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcfbe3f777a6963832e0b8f5f8c9acd483d7a06214da4f94659c7a65b3e9f7a4" } } ], "extra": [ 1, 216, 49, 65, 3, 30, 0, 245, 246, 237, 230, 72, 165, 141, 187, 112, 246, 45, 147, 220, 234, 232, 94, 198, 241, 164, 229, 146, 210, 45, 219, 93, 185, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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