Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea587072ab3a6d6106cb3ccbe19a5909d538924dca444712affc078b7766fcbd

Tx prefix hash: ba13fa0c550e0a05aa0087b08a62acd8ad244ecc09e638a6596974c7f4d667dd
Tx public key: 2dae27cfc49650c7a80c208b411fc1fd187784e4f5454541b4afb7ebe502b120
Timestamp: 1695649784 Timestamp [UCT]: 2023-09-25 13:49:44 Age [y:d:h:m:s]: 01:196:06:16:52
Block: 855878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401328 RingCT/type: yes/0
Extra: 012dae27cfc49650c7a80c208b411fc1fd187784e4f5454541b4afb7ebe502b12002110000000475e3f0e9000000000000000000

1 output(s) for total of 0.895614141000 dcy

stealth address amount amount idx
00: ee0fb84487164550e3cae697d63f8ef91f9f2bc2ba584f4744b02c7918f8e579 0.895614141000 1309926 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": 855888, "vin": [ { "gen": { "height": 855878 } } ], "vout": [ { "amount": 895614141, "target": { "key": "ee0fb84487164550e3cae697d63f8ef91f9f2bc2ba584f4744b02c7918f8e579" } } ], "extra": [ 1, 45, 174, 39, 207, 196, 150, 80, 199, 168, 12, 32, 139, 65, 31, 193, 253, 24, 119, 132, 228, 245, 69, 69, 65, 180, 175, 183, 235, 229, 2, 177, 32, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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