Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 227e96e69a2b526f8fc4e5dc7f729884cdc5fd37e9ad82f9bc785d43c874c8e0

Tx prefix hash: f8cd746e05ba6b7952d9bfe6c0cd26f6e27301c3e4f3a9d99b92e45af67dde26
Tx public key: ce237cfa2f20ae7b7f027e545843ecab4ce611a348e95207399bd2a836faf5f8
Timestamp: 1711739984 Timestamp [UCT]: 2024-03-29 19:19:44 Age [y:d:h:m:s]: 00:287:00:51:33
Block: 989101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205442 RingCT/type: yes/0
Extra: 01ce237cfa2f20ae7b7f027e545843ecab4ce611a348e95207399bd2a836faf5f80211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4f1d8f5fbd9b1057758509b587a3a7237a6c6bfdcfa3a60e7b6a0396dc90c78 0.600000000000 1449396 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": 989111, "vin": [ { "gen": { "height": 989101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4f1d8f5fbd9b1057758509b587a3a7237a6c6bfdcfa3a60e7b6a0396dc90c78" } } ], "extra": [ 1, 206, 35, 124, 250, 47, 32, 174, 123, 127, 2, 126, 84, 88, 67, 236, 171, 76, 230, 17, 163, 72, 233, 82, 7, 57, 155, 210, 168, 54, 250, 245, 248, 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