Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c54d701b149c5a95c0f2a676cb7c4b47f12200bbf28401c12cb27be4790c8a7

Tx prefix hash: 9e28c99c79fc8886115925291b721416fbe361df1c6e4326628bdc1d6f9ecebd
Tx public key: bd81201e189b161d2d266d5183643f55ac5b76ced50bc015e31fb693a02de198
Timestamp: 1718202849 Timestamp [UCT]: 2024-06-12 14:34:09 Age [y:d:h:m:s]: 00:337:23:04:12
Block: 1042671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241530 RingCT/type: yes/0
Extra: 01bd81201e189b161d2d266d5183643f55ac5b76ced50bc015e31fb693a02de1980211000000058fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25137a420b9c05f8e2f900c82aa30e93c8e7aa07522a240a125d564cc7ec0f28 0.600000000000 1511642 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": 1042681, "vin": [ { "gen": { "height": 1042671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25137a420b9c05f8e2f900c82aa30e93c8e7aa07522a240a125d564cc7ec0f28" } } ], "extra": [ 1, 189, 129, 32, 30, 24, 155, 22, 29, 45, 38, 109, 81, 131, 100, 63, 85, 172, 91, 118, 206, 213, 11, 192, 21, 227, 31, 182, 147, 160, 45, 225, 152, 2, 17, 0, 0, 0, 5, 143, 218, 155, 45, 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