Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 275c727fbc06003a88ab871083f80055c5e57a00ca7f44301e6d61775c4ccf8b

Tx prefix hash: d8167bc3b7827e69e2bc37ed9e85c9f6fcecd2ce575ccde32e24d979e7a405f4
Tx public key: bf3d61803d8bf546f0708a28b4801235d2ef4004b662c8de6348e3fb2ec4dc94
Timestamp: 1717330005 Timestamp [UCT]: 2024-06-02 12:06:45 Age [y:d:h:m:s]: 00:287:17:57:19
Block: 1035428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205645 RingCT/type: yes/0
Extra: 01bf3d61803d8bf546f0708a28b4801235d2ef4004b662c8de6348e3fb2ec4dc940211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a39218d9fe3bb65fd04f7d1cecf123275368b3c2b4a171d9c0e44980948c8115 0.600000000000 1503949 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": 1035438, "vin": [ { "gen": { "height": 1035428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a39218d9fe3bb65fd04f7d1cecf123275368b3c2b4a171d9c0e44980948c8115" } } ], "extra": [ 1, 191, 61, 97, 128, 61, 139, 245, 70, 240, 112, 138, 40, 180, 128, 18, 53, 210, 239, 64, 4, 182, 98, 200, 222, 99, 72, 227, 251, 46, 196, 220, 148, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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