Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8a239f7659f818826e972b86324fa196ed33c3b738c5c0f57ee93e0aab945c0

Tx prefix hash: a1159c0a64bc9cce7540fb8b39b493f311c488ec5d30fe155ce1fb7adfde9390
Tx public key: 77d4066506f5b829af896b6346f6a80c37d2f096c716d3cb70a0c0cdb6434cb1
Timestamp: 1745563276 Timestamp [UCT]: 2025-04-25 06:41:16 Age [y:d:h:m:s]: 00:242:05:44:52
Block: 1268977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170878 RingCT/type: yes/0
Extra: 0177d4066506f5b829af896b6346f6a80c37d2f096c716d3cb70a0c0cdb6434cb1021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc273c0dd3a3fa1cf33303e0d71afced7f94d6ec5402e8fa7c8ceb06ff9f4d1e 0.600000000000 1756210 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": 1268987, "vin": [ { "gen": { "height": 1268977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc273c0dd3a3fa1cf33303e0d71afced7f94d6ec5402e8fa7c8ceb06ff9f4d1e" } } ], "extra": [ 1, 119, 212, 6, 101, 6, 245, 184, 41, 175, 137, 107, 99, 70, 246, 168, 12, 55, 210, 240, 150, 199, 22, 211, 203, 112, 160, 192, 205, 182, 67, 76, 177, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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