Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b8ff311be5cd761ee3764179915b1115b1269a46e2cf847a0b15999de052941

Tx prefix hash: 48074d993138c4e7ca8689dbdaebdc0f6caba412fd5269a2ba46f89821318b0e
Tx public key: b0dac02f387600377ea4c1241a15b99bf04c5cb4f5e3b3db6b6fa95451d14987
Timestamp: 1736573620 Timestamp [UCT]: 2025-01-11 05:33:40 Age [y:d:h:m:s]: 00:113:21:40:09
Block: 1194822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81194 RingCT/type: yes/0
Extra: 01b0dac02f387600377ea4c1241a15b99bf04c5cb4f5e3b3db6b6fa95451d14987021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 886c3aaa25a1f88da81ca7a9936a0f837fbf755a75a212b13eab13e7971965d8 0.600000000000 1681399 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": 1194832, "vin": [ { "gen": { "height": 1194822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "886c3aaa25a1f88da81ca7a9936a0f837fbf755a75a212b13eab13e7971965d8" } } ], "extra": [ 1, 176, 218, 192, 47, 56, 118, 0, 55, 126, 164, 193, 36, 26, 21, 185, 155, 240, 76, 92, 180, 245, 227, 179, 219, 107, 111, 169, 84, 81, 209, 73, 135, 2, 17, 0, 0, 0, 6, 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