Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1b0993a53db92f79fe604f27a868799a2605b3e61e5c8c95ee696c20ac96dc2

Tx prefix hash: 2a90152ef27d3ae38a5441e53c7b40a96a774c741d6671f30db6438bc46e48be
Tx public key: 1e53c0e43a1b6de08b4e679be9bc861a77154395d8d7836aefbac6b5ab7914da
Timestamp: 1582522934 Timestamp [UCT]: 2020-02-24 05:42:14 Age [y:d:h:m:s]: 05:096:00:43:53
Block: 71609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221698 RingCT/type: yes/0
Extra: 011e53c0e43a1b6de08b4e679be9bc861a77154395d8d7836aefbac6b5ab7914da0211000000018a2ee0d9000000000000000000

1 output(s) for total of 355.410666831000 dcy

stealth address amount amount idx
00: 4d097aaf3e18eb73633f487aabaf095913964ee56d69521082ef273efec9a6ba 355.410666831000 132198 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": 71619, "vin": [ { "gen": { "height": 71609 } } ], "vout": [ { "amount": 355410666831, "target": { "key": "4d097aaf3e18eb73633f487aabaf095913964ee56d69521082ef273efec9a6ba" } } ], "extra": [ 1, 30, 83, 192, 228, 58, 27, 109, 224, 139, 78, 103, 155, 233, 188, 134, 26, 119, 21, 67, 149, 216, 215, 131, 106, 239, 186, 198, 181, 171, 121, 20, 218, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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