Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a28b69811fa9d6a53fba1ebca26cc361e9962c9df6aa536fca25ad7ae5a339a

Tx prefix hash: bbfd80497aba9395b31e3f19910ef47a7e64a0a21a4b166beeb4f74624b86729
Tx public key: aaa0f2ab122272b4ff5441c0db2c1d709da3fff2f7d9678e04e5f5e1f5c4a843
Timestamp: 1722931283 Timestamp [UCT]: 2024-08-06 08:01:23 Age [y:d:h:m:s]: 00:243:04:23:56
Block: 1081854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173689 RingCT/type: yes/0
Extra: 01aaa0f2ab122272b4ff5441c0db2c1d709da3fff2f7d9678e04e5f5e1f5c4a84302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d05edcf0b6ff3e213f018892408820e8acd6d9fcd8ba4628eed4b328f007ac19 0.600000000000 1555677 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": 1081864, "vin": [ { "gen": { "height": 1081854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d05edcf0b6ff3e213f018892408820e8acd6d9fcd8ba4628eed4b328f007ac19" } } ], "extra": [ 1, 170, 160, 242, 171, 18, 34, 114, 180, 255, 84, 65, 192, 219, 44, 29, 112, 157, 163, 255, 242, 247, 217, 103, 142, 4, 229, 245, 225, 245, 196, 168, 67, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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