Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10e6a672dca44bddccadbfb0a3195321cf6d5b033b67f16c6427e3d8eb880376

Tx prefix hash: baab91d0a71c5450d00f5f2f51109b4fdbbecf5ae14b81e26748d964e83b61d2
Tx public key: 882aa892e53936676b7b593a9a2063c728078ce9125ef92f0cd1eae29e185682
Timestamp: 1681765167 Timestamp [UCT]: 2023-04-17 20:59:27 Age [y:d:h:m:s]: 01:197:22:36:17
Block: 740811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402908 RingCT/type: yes/0
Extra: 01882aa892e53936676b7b593a9a2063c728078ce9125ef92f0cd1eae29e18568202110000000175e3f0e9000000000000000000

1 output(s) for total of 2.154695221000 dcy

stealth address amount amount idx
00: 56fa0d1a19c68db79d7695ee28ef67be5896a6ee999cf146ed54edf3297f6e04 2.154695221000 1187716 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 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": 740821, "vin": [ { "gen": { "height": 740811 } } ], "vout": [ { "amount": 2154695221, "target": { "key": "56fa0d1a19c68db79d7695ee28ef67be5896a6ee999cf146ed54edf3297f6e04" } } ], "extra": [ 1, 136, 42, 168, 146, 229, 57, 54, 103, 107, 123, 89, 58, 154, 32, 99, 199, 40, 7, 140, 233, 18, 94, 249, 47, 12, 209, 234, 226, 158, 24, 86, 130, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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