Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9650758e210625c1844ae42802895629ece582fe0d24dd3e1c5caf1ad2dda2a

Tx prefix hash: c4bf0476bd61ef94fedf92bfd9a27ce429165d8fb06cfb3d7fbd3f61f4c14a53
Tx public key: 3ffebfc138e82b02595aae4cd6bed2935ff0f2d7c77ecec312aa3558cdb42fdb
Timestamp: 1719228065 Timestamp [UCT]: 2024-06-24 11:21:05 Age [y:d:h:m:s]: 01:137:18:18:30
Block: 1051144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357016 RingCT/type: yes/0
Extra: 013ffebfc138e82b02595aae4cd6bed2935ff0f2d7c77ecec312aa3558cdb42fdb0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 620d03b4119cfdfa57ab1a54c96bd852f7be62bd68e7db0e9a376264aab33147 0.600000000000 1521411 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": 1051154, "vin": [ { "gen": { "height": 1051144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "620d03b4119cfdfa57ab1a54c96bd852f7be62bd68e7db0e9a376264aab33147" } } ], "extra": [ 1, 63, 254, 191, 193, 56, 232, 43, 2, 89, 90, 174, 76, 214, 190, 210, 147, 95, 240, 242, 215, 199, 126, 206, 195, 18, 170, 53, 88, 205, 180, 47, 219, 2, 17, 0, 0, 0, 2, 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