Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e2485dd99d25dbe044492f4b8cfa291da5b2fdd54b43d43efd217eff24d95bd

Tx prefix hash: ed55980f652b4aba8c2a0c17536a1d5c366eead41fdb71adc3865af56e4a1041
Tx public key: 14f458a0f8d8d3a896f56c3c906c9a082d1505102755541c5acf6204d76b7ad1
Timestamp: 1728840618 Timestamp [UCT]: 2024-10-13 17:30:18 Age [y:d:h:m:s]: 00:239:13:07:28
Block: 1130847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171035 RingCT/type: yes/0
Extra: 0114f458a0f8d8d3a896f56c3c906c9a082d1505102755541c5acf6204d76b7ad1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f77ec8b4fe67019b3e0dd6de6d79e0470e7a40650f5dc1d735f2e8e15f6ee8b4 0.600000000000 1613728 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": 1130857, "vin": [ { "gen": { "height": 1130847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f77ec8b4fe67019b3e0dd6de6d79e0470e7a40650f5dc1d735f2e8e15f6ee8b4" } } ], "extra": [ 1, 20, 244, 88, 160, 248, 216, 211, 168, 150, 245, 108, 60, 144, 108, 154, 8, 45, 21, 5, 16, 39, 85, 84, 28, 90, 207, 98, 4, 215, 107, 122, 209, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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