Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0fd9c1e7ab653874347b91a4ea34d41cd9c5da9000c694cf2a75cf48f01e805

Tx prefix hash: 523d89964f1b6060bc4e2d6d1628a4d8926f058965d42ccef246a228744d516c
Tx public key: 929e863f77e583ac40602f1a65bbad00292133e66f5e4be9f9d8682e389f58f0
Timestamp: 1707707688 Timestamp [UCT]: 2024-02-12 03:14:48 Age [y:d:h:m:s]: 00:314:21:53:30
Block: 955636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225495 RingCT/type: yes/0
Extra: 01929e863f77e583ac40602f1a65bbad00292133e66f5e4be9f9d8682e389f58f00211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bda267b5855867e623995bd3ae81a7d5b0ba8e9a90a0247d5169059d40bca5e 0.600000000000 1414934 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": 955646, "vin": [ { "gen": { "height": 955636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bda267b5855867e623995bd3ae81a7d5b0ba8e9a90a0247d5169059d40bca5e" } } ], "extra": [ 1, 146, 158, 134, 63, 119, 229, 131, 172, 64, 96, 47, 26, 101, 187, 173, 0, 41, 33, 51, 230, 111, 94, 75, 233, 249, 216, 104, 46, 56, 159, 88, 240, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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