Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feb31616e1de46800928ed889fa918e201a6f64f22e1e843b4e180deee0b91fd

Tx prefix hash: be98e32547bc4b6d55302e6e88837c6908dfe9ac526ec6d772a4df46b9492217
Tx public key: 2264d70db26d47c8e8a4d6f37099f8f45185e2ae81a39d7e985de37cde59f820
Timestamp: 1702226054 Timestamp [UCT]: 2023-12-10 16:34:14 Age [y:d:h:m:s]: 01:037:00:10:51
Block: 910194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287804 RingCT/type: yes/0
Extra: 012264d70db26d47c8e8a4d6f37099f8f45185e2ae81a39d7e985de37cde59f820021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2194eff4680b5e35f251ea26f713dd87959b6fa49ddd05556afb700260ceb0a 0.600000000000 1367339 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": 910204, "vin": [ { "gen": { "height": 910194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2194eff4680b5e35f251ea26f713dd87959b6fa49ddd05556afb700260ceb0a" } } ], "extra": [ 1, 34, 100, 215, 13, 178, 109, 71, 200, 232, 164, 214, 243, 112, 153, 248, 244, 81, 133, 226, 174, 129, 163, 157, 126, 152, 93, 227, 124, 222, 89, 248, 32, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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