Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 428096b990c25407dedce2553a7d82da27b2adaeecbd7ae9e7b5472f04d69cdf

Tx prefix hash: b9208d6341ff517f7ec09f7360b026f1485e95b20d8c389e13fa5b8458a4964c
Tx public key: fbac3ba68b93ba06f1f0ed1223cb1b99eabcf89ebd846f91046d639a5c4d092a
Timestamp: 1713408485 Timestamp [UCT]: 2024-04-18 02:48:05 Age [y:d:h:m:s]: 00:313:21:27:32
Block: 1002895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224385 RingCT/type: yes/0
Extra: 01fbac3ba68b93ba06f1f0ed1223cb1b99eabcf89ebd846f91046d639a5c4d092a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d2130cd89d56b17961de6f66b89b22bdbcbad236b379de00bd4742ad2d9e9c9 0.600000000000 1463425 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": 1002905, "vin": [ { "gen": { "height": 1002895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d2130cd89d56b17961de6f66b89b22bdbcbad236b379de00bd4742ad2d9e9c9" } } ], "extra": [ 1, 251, 172, 59, 166, 139, 147, 186, 6, 241, 240, 237, 18, 35, 203, 27, 153, 234, 188, 248, 158, 189, 132, 111, 145, 4, 109, 99, 154, 92, 77, 9, 42, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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