Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bb983bb6ee77786e614b7e346f711d5ca123ccb3d12abea1fb86546d5635f37

Tx prefix hash: ff1853efc35645ae2aaecb7f2a30191f24dcf26f517d0687b6f045412b43a0c9
Tx public key: e4702a42f7b3222d829cf72e26e282e8000108ed5a917908c5b9ba4209f45f7f
Timestamp: 1697366527 Timestamp [UCT]: 2023-10-15 10:42:07 Age [y:d:h:m:s]: 01:173:08:26:20
Block: 870116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384913 RingCT/type: yes/0
Extra: 01e4702a42f7b3222d829cf72e26e282e8000108ed5a917908c5b9ba4209f45f7f021100000001faf35c9c000000000000000000

1 output(s) for total of 0.803423474000 dcy

stealth address amount amount idx
00: 04321a3e2c45072f3f8cb65cafb436a6b6a1eacd72777ba8aa877ddfe2f7c58a 0.803423474000 1324989 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": 870126, "vin": [ { "gen": { "height": 870116 } } ], "vout": [ { "amount": 803423474, "target": { "key": "04321a3e2c45072f3f8cb65cafb436a6b6a1eacd72777ba8aa877ddfe2f7c58a" } } ], "extra": [ 1, 228, 112, 42, 66, 247, 179, 34, 45, 130, 156, 247, 46, 38, 226, 130, 232, 0, 1, 8, 237, 90, 145, 121, 8, 197, 185, 186, 66, 9, 244, 95, 127, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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