Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48a0a919f6c9ebfdac88cc6f7f2e89480c853c1cc715eff49d01e14a62f37b5d

Tx prefix hash: 1c8a9ac6a0200700c575ad7a0769618934d0e3283a188d92bb58a6e5cdc034c5
Tx public key: 7a25c7bab7b48b1706306cf802c9c71044d0f650ef17c811dfd7a6c7bb002412
Timestamp: 1574743263 Timestamp [UCT]: 2019-11-26 04:41:03 Age [y:d:h:m:s]: 05:041:23:03:30
Block: 17651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172826 RingCT/type: yes/0
Extra: 017a25c7bab7b48b1706306cf802c9c71044d0f650ef17c811dfd7a6c7bb00241202110000000bb63f0b49000000000000000000

1 output(s) for total of 536.457354624000 dcy

stealth address amount amount idx
00: bfd07aa44db9cd50c1c805d218e6254dbe2f102c7acb76d6af90836c51d817c8 536.457354624000 25964 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": 17661, "vin": [ { "gen": { "height": 17651 } } ], "vout": [ { "amount": 536457354624, "target": { "key": "bfd07aa44db9cd50c1c805d218e6254dbe2f102c7acb76d6af90836c51d817c8" } } ], "extra": [ 1, 122, 37, 199, 186, 183, 180, 139, 23, 6, 48, 108, 248, 2, 201, 199, 16, 68, 208, 246, 80, 239, 23, 200, 17, 223, 215, 166, 199, 187, 0, 36, 18, 2, 17, 0, 0, 0, 11, 182, 63, 11, 73, 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