Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e2b0eac055de568bb19cbc6f2e80fda9c63ad95f8a25da213a99f9f0996714f

Tx prefix hash: e99fc5cf3a022de14cbdfd4c8c8ffc37fb9d5d23aec2e91374e704b3dd7b4189
Tx public key: bb2d3796a185f5f2a40565bb2ae23cb9593518c7aba66408d4ae18169a16eb60
Timestamp: 1683374105 Timestamp [UCT]: 2023-05-06 11:55:05 Age [y:d:h:m:s]: 01:297:22:07:11
Block: 754165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474129 RingCT/type: yes/0
Extra: 01bb2d3796a185f5f2a40565bb2ae23cb9593518c7aba66408d4ae18169a16eb6002110000000133af99f4000000000000000000

1 output(s) for total of 1.945980496000 dcy

stealth address amount amount idx
00: eea72d3aee6e040a3e65383ee7391d07d3cf3c4a0f3e17fb22ee0b15a9ba08f8 1.945980496000 1202418 of 0

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": 754175, "vin": [ { "gen": { "height": 754165 } } ], "vout": [ { "amount": 1945980496, "target": { "key": "eea72d3aee6e040a3e65383ee7391d07d3cf3c4a0f3e17fb22ee0b15a9ba08f8" } } ], "extra": [ 1, 187, 45, 55, 150, 161, 133, 245, 242, 164, 5, 101, 187, 42, 226, 60, 185, 89, 53, 24, 199, 171, 166, 100, 8, 212, 174, 24, 22, 154, 22, 235, 96, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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