Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1aa449fdc754cd1254e24b7b06524755efaa421ea511cc98ecd49438bfeeec

Tx prefix hash: c33fa8f1d9f3e76cbac0d2b56eed198d27c06010e7198c9492e29350b50469ae
Tx public key: 213efa65174931dd82643ea538c37a2d228573564a4030c186b7006e6c9d5f38
Timestamp: 1637472122 Timestamp [UCT]: 2021-11-21 05:22:02 Age [y:d:h:m:s]: 02:350:05:18:17
Block: 378773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 768260 RingCT/type: yes/0
Extra: 01213efa65174931dd82643ea538c37a2d228573564a4030c186b7006e6c9d5f38021100000001379224c2000000000000000000

1 output(s) for total of 34.117382758000 dcy

stealth address amount amount idx
00: 19ae5ead325ba7e2746e3df12f0f7cfe4f233e2666ee654e444ff63e8f5eced0 34.117382758000 765855 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": 378783, "vin": [ { "gen": { "height": 378773 } } ], "vout": [ { "amount": 34117382758, "target": { "key": "19ae5ead325ba7e2746e3df12f0f7cfe4f233e2666ee654e444ff63e8f5eced0" } } ], "extra": [ 1, 33, 62, 250, 101, 23, 73, 49, 221, 130, 100, 62, 165, 56, 195, 122, 45, 34, 133, 115, 86, 74, 64, 48, 193, 134, 183, 0, 110, 108, 157, 95, 56, 2, 17, 0, 0, 0, 1, 55, 146, 36, 194, 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