Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0b8f768aa35e393d6edd583144a5b3c63d7d904437837d0f3da194e7be8751e

Tx prefix hash: 27ed011210a5566d67058d712318fdabf8ee9b6f837fd4bc88e4a51cf9eca81f
Tx public key: 54d3e10746990d1035f802cca7999ac5d20b63d215467f6dc6bdf97a4cf5f8a0
Timestamp: 1731053814 Timestamp [UCT]: 2024-11-08 08:16:54 Age [y:d:h:m:s]: 00:221:16:37:12
Block: 1149116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158187 RingCT/type: yes/0
Extra: 0154d3e10746990d1035f802cca7999ac5d20b63d215467f6dc6bdf97a4cf5f8a0021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5705ce3453b9cf719b767fa4414b1b851e3ecaff8974e72549c57a033e9f2f77 0.600000000000 1634121 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": 1149126, "vin": [ { "gen": { "height": 1149116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5705ce3453b9cf719b767fa4414b1b851e3ecaff8974e72549c57a033e9f2f77" } } ], "extra": [ 1, 84, 211, 225, 7, 70, 153, 13, 16, 53, 248, 2, 204, 167, 153, 154, 197, 210, 11, 99, 210, 21, 70, 127, 109, 198, 189, 249, 122, 76, 245, 248, 160, 2, 17, 0, 0, 0, 1, 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