Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 790c81562e6da00924cc57b9f5df78a69f9a5934f9ae1077996ab4230be6e4f8

Tx prefix hash: 1025d7a3192f325d0a95bf44a590b93ad161591f6c4dce312a3f0342e57fc44f
Tx public key: 7612b716e301091731c8bdfa84a7088b390a55ee23d04f33707d475c699e4ab3
Timestamp: 1734788426 Timestamp [UCT]: 2024-12-21 13:40:26 Age [y:d:h:m:s]: 00:093:06:35:40
Block: 1180067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66416 RingCT/type: yes/0
Extra: 017612b716e301091731c8bdfa84a7088b390a55ee23d04f33707d475c699e4ab302110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 022e1c9bcea6ec697f983eaff8a701fc9a997d2fd0cfda546cff481c6ba8be6c 0.600000000000 1666472 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": 1180077, "vin": [ { "gen": { "height": 1180067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "022e1c9bcea6ec697f983eaff8a701fc9a997d2fd0cfda546cff481c6ba8be6c" } } ], "extra": [ 1, 118, 18, 183, 22, 227, 1, 9, 23, 49, 200, 189, 250, 132, 167, 8, 139, 57, 10, 85, 238, 35, 208, 79, 51, 112, 125, 71, 92, 105, 158, 74, 179, 2, 17, 0, 0, 0, 13, 0, 127, 151, 138, 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