Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c94fa26a1faeb70f49e9cab60e8fbf0d0ed3c2f98668543e79e82abab177c97

Tx prefix hash: f10014dc1ddec79f200f20a6add548ecc2f94972216d18276cdb25ec080c7165
Tx public key: 56e8e204a17a445d2d25dd6c6ecb8de4771e0b98a03bd8d940dd6bd3ee84af56
Timestamp: 1730457391 Timestamp [UCT]: 2024-11-01 10:36:31 Age [y:d:h:m:s]: 00:147:21:19:03
Block: 1144166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105524 RingCT/type: yes/0
Extra: 0156e8e204a17a445d2d25dd6c6ecb8de4771e0b98a03bd8d940dd6bd3ee84af560211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc131c5501ccd09673755f6944a99d6d4f7c1004fe8fbe4cd6b26888e837680c 0.600000000000 1628289 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": 1144176, "vin": [ { "gen": { "height": 1144166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc131c5501ccd09673755f6944a99d6d4f7c1004fe8fbe4cd6b26888e837680c" } } ], "extra": [ 1, 86, 232, 226, 4, 161, 122, 68, 93, 45, 37, 221, 108, 110, 203, 141, 228, 119, 30, 11, 152, 160, 59, 216, 217, 64, 221, 107, 211, 238, 132, 175, 86, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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