Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf680b6a720af17b4712b0bda6ca1b6f48e5a9a2c8b228da7c8876e073eac0a2

Tx prefix hash: 542a1cdd60a53a35a39aab169b0bbe74246957ced9dc16e73c8e742a25f86895
Tx public key: 5610cdd1d0b4fc3d804f74c1f40f1f85a2999b210c780b2b6414e92d01aa5f78
Timestamp: 1648471571 Timestamp [UCT]: 2022-03-28 12:46:11 Age [y:d:h:m:s]: 02:054:00:01:53
Block: 468198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 557930 RingCT/type: yes/0
Extra: 015610cdd1d0b4fc3d804f74c1f40f1f85a2999b210c780b2b6414e92d01aa5f78021100000005c9067537000000000000000000

1 output(s) for total of 17.245108053000 dcy

stealth address amount amount idx
00: fe0a54409e1dbf42467ffdfba5e7b0fdf4eca59aba971e68acd441c714145010 17.245108053000 886856 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": 468208, "vin": [ { "gen": { "height": 468198 } } ], "vout": [ { "amount": 17245108053, "target": { "key": "fe0a54409e1dbf42467ffdfba5e7b0fdf4eca59aba971e68acd441c714145010" } } ], "extra": [ 1, 86, 16, 205, 209, 208, 180, 252, 61, 128, 79, 116, 193, 244, 15, 31, 133, 162, 153, 155, 33, 12, 120, 11, 43, 100, 20, 233, 45, 1, 170, 95, 120, 2, 17, 0, 0, 0, 5, 201, 6, 117, 55, 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