Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b58b8f04a238a79c57ee7e3adb1b3f9128d9f92ec398a066fc7f85c7ed80044d

Tx prefix hash: 580ba5fd86ab8b44a34bc276d02b9a85c4c17f6a0c407a2bce775ae9fecc9df0
Tx public key: 1f59698a68099573257f44ac49ed94957cd0301ea90977b20636e4a6b4f489a1
Timestamp: 1703529030 Timestamp [UCT]: 2023-12-25 18:30:30 Age [y:d:h:m:s]: 01:098:12:30:39
Block: 921000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331517 RingCT/type: yes/0
Extra: 011f59698a68099573257f44ac49ed94957cd0301ea90977b20636e4a6b4f489a102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09eef5025643c772d0bdb464ecf3a1a353b8b6ef5b5ebf3bf4ea4d435c436449 0.600000000000 1378684 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": 921010, "vin": [ { "gen": { "height": 921000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09eef5025643c772d0bdb464ecf3a1a353b8b6ef5b5ebf3bf4ea4d435c436449" } } ], "extra": [ 1, 31, 89, 105, 138, 104, 9, 149, 115, 37, 127, 68, 172, 73, 237, 148, 149, 124, 208, 48, 30, 169, 9, 119, 178, 6, 54, 228, 166, 180, 244, 137, 161, 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