Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1b1cab568684d09bff03d7b692f450d160bfafffb5db1a38fa7633c9ad25545

Tx prefix hash: 287b6b98bc02efe033be2e8e9bb89337d25ef9d019efa3056a2af63528c48a96
Tx public key: 296da724fe38d0bc4e3fcbf08213e4ddc2eeefdb29065f511c811ce1af85363a
Timestamp: 1705296895 Timestamp [UCT]: 2024-01-15 05:34:55 Age [y:d:h:m:s]: 00:359:23:27:41
Block: 935631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257738 RingCT/type: yes/0
Extra: 01296da724fe38d0bc4e3fcbf08213e4ddc2eeefdb29065f511c811ce1af85363a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2b0cc149b8d3ed80c5d3f97e9f251a223826f8e27d5dfebea0243a8cde0c238 0.600000000000 1393647 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": 935641, "vin": [ { "gen": { "height": 935631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2b0cc149b8d3ed80c5d3f97e9f251a223826f8e27d5dfebea0243a8cde0c238" } } ], "extra": [ 1, 41, 109, 167, 36, 254, 56, 208, 188, 78, 63, 203, 240, 130, 19, 228, 221, 194, 238, 239, 219, 41, 6, 95, 81, 28, 129, 28, 225, 175, 133, 54, 58, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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