Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db421c38a4b79c110ecf4dd961df68cb6f9fc93a0fdbbc052a9261f1f8db6a91

Tx prefix hash: f1e79598403a59e0147a8f1bd56e29fd1e315e4fff9cd000d20b004cdadd7f15
Tx public key: ddbbf398a230a2e836e2b0bacf99926e729a1d11804d896b235aa82b9f600c23
Timestamp: 1711722916 Timestamp [UCT]: 2024-03-29 14:35:16 Age [y:d:h:m:s]: 01:045:01:35:47
Block: 988955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293179 RingCT/type: yes/0
Extra: 01ddbbf398a230a2e836e2b0bacf99926e729a1d11804d896b235aa82b9f600c2302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b845f0b7c0b11984c01a1abcbaa4ef2d321b801e8fa6accb5c9abdc7f9104a5b 0.600000000000 1449246 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": 988965, "vin": [ { "gen": { "height": 988955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b845f0b7c0b11984c01a1abcbaa4ef2d321b801e8fa6accb5c9abdc7f9104a5b" } } ], "extra": [ 1, 221, 187, 243, 152, 162, 48, 162, 232, 54, 226, 176, 186, 207, 153, 146, 110, 114, 154, 29, 17, 128, 77, 137, 107, 35, 90, 168, 43, 159, 96, 12, 35, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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