Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c87c9f403666960287183e048e4e42db65ddfc16913be0bd5d69286fc3556e9

Tx prefix hash: 31c0b75f6dbb3755a7c19816050d661ef3a85acef96c2d84deb7d561ecea2c83
Tx public key: b1020013a6b579f60b2374343c00e87ea06be8900a499ca390c09dac70cdb4d5
Timestamp: 1638396887 Timestamp [UTC]: 2021-12-01 22:14:47 Age [y:d:h:m:s]: 04:170:21:46:14
Block: 386374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1152850 RingCT/type: yes/0
Extra: 01b1020013a6b579f60b2374343c00e87ea06be8900a499ca390c09dac70cdb4d5021100000002f6cc1430000000000000000000

1 output(s) for total of 0.032194591424 xmr

stealth address amount amount idx tag
00: 4bbec39757e64bd1421be82efb9ccfff7a82320080026c3344dedfe312135a2d 0.032194591424 779517 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 dinastycoin-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": 386384, "vin": [ { "gen": { "height": 386374 } } ], "vout": [ { "amount": 32194591424, "target": { "key": "4bbec39757e64bd1421be82efb9ccfff7a82320080026c3344dedfe312135a2d" } } ], "extra": [ 1, 177, 2, 0, 19, 166, 181, 121, 246, 11, 35, 116, 52, 60, 0, 232, 126, 160, 107, 232, 144, 10, 73, 156, 163, 144, 192, 157, 172, 112, 205, 180, 213, 2, 17, 0, 0, 0, 2, 246, 204, 20, 48, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: