Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c802621d1bc39ec940c901a02129a0416c260b35b1e11665ec81a1cd60aa4606

Tx prefix hash: e1b580716d1461746c567665d6af5c3390293bad3a48e29ebd6ab25d7213c99c
Tx public key: 6d98d1c55a302cbf655074d87d70064c76bceec9e69d9e08ecc425c7f2c6f7ec
Timestamp: 1698455247 Timestamp [UCT]: 2023-10-28 01:07:27 Age [y:d:h:m:s]: 01:234:00:05:38
Block: 879154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428164 RingCT/type: yes/0
Extra: 016d98d1c55a302cbf655074d87d70064c76bceec9e69d9e08ecc425c7f2c6f7ec02110000000efaf35c9c000000000000000000

1 output(s) for total of 0.749890510000 dcy

stealth address amount amount idx
00: 194d1db0d8ba49b96faf93a71e15def8b1ea0d7322ae0f617472ef2ae37e5de9 0.749890510000 1334656 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": 879164, "vin": [ { "gen": { "height": 879154 } } ], "vout": [ { "amount": 749890510, "target": { "key": "194d1db0d8ba49b96faf93a71e15def8b1ea0d7322ae0f617472ef2ae37e5de9" } } ], "extra": [ 1, 109, 152, 209, 197, 90, 48, 44, 191, 101, 80, 116, 216, 125, 112, 6, 76, 118, 188, 238, 201, 230, 157, 158, 8, 236, 196, 37, 199, 242, 198, 247, 236, 2, 17, 0, 0, 0, 14, 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